|
|
|
|
|
Hi Younkwang, We have not been able to reproduce the issue yet. What is the probability of the issue happening? Does the issue happen to many DUTs? Thank you Dean Chiang |
|
|
Hi Mr. Dean Chiang, We produced it whenever we would like to reproduce with 2nd source b'd that used a Motorcomm PHY. Could you try 20 times with 2~3 STBs for reproduce this issue ? We think that this issue occur only for 2nd source b'd, not Realtek PHY. So it should be fixed if we have some bug on SW/HW side. And could you check with your vendor about this issue ? They may know about this issue and they also have solution. Best regards, SuhYoung YOON |
|
|
Hi Mr. SY Yoon, I have tried 20 times with 3 STBs(second source). But still can't reproduce it. Can you provide a video of this issue? I may need to reproduce it then check with our vendor. Thank you Dean Chiang |
|
|
Hi Mr. SY Yoon, Can you provide dmesg log when the issue occurs? Is DUT really unable to connect to the Internet or just UI shows? We want to analyze whether the issue is with the UI or the driver. Thank you Dean |
|
|
HI Dean If I test again now, after entering a different menu from the network error popup window, connect the LAN cable It seems to happen more often. ( there were times when the issue did not occur when tested for 3 to 4 hours.) Attach the log file. (dmesg/logcat) The last state is the LAN cable plugged in, but the network error pop-up is displayed. Thank you YK.Jung |
|
|
Hi Younkwang, We need more information to analyze this issue. I upload a new test fw to ftp server. It prints more driver log. Path: /release_by_fxn/smart3_test/network_error/ Can you help update fw and provide dmesg and logcat? Thank you Dean Chiang |
|
|
Hi Younkwang, Currently we can't reproduce this issue according to your steps exactly. Please provide login accounts for below MACs. 38:d5:7a:d9:3e:c8 38:d5:7a:d9:3e:c7 38:d5:7a:d9:3e:cb 38:d5:7a:d9:3e:9d We tried ATT test account on 2nd source board, but it didn't work. Is there any MAC limitation for ATT test account? |
|
|
HI Bcan. Do you want to log in for your mac list board? if yes, you need to receive login accounts. Is there any MAC limitation for ATT test account? --> There is no limitation. if you have master key, you can use it. it means that key is using for factory line. Best Regards Jason.park |
|
|
Hi Bcan I will request the login account for the MACs you requested to SKB. However, SKB is off today, so I don't think I can get it today. I will update you as soon as I receive account information from SKB And I will proceed with the network test you requested next Tuesday (Aug/16th) Thank you YK.Jung |
|
|
Hi Bcan, If you use ATT test account, then the Mac should be registered on SKB system. So please use same MAC that you tested. Anyway you can use authentication key that you already used before. But it should be use same MAC address. BR S Yoon. |
|
|
Hi Younkwang, Vendor still need more information to analyze this issue. Bcan and I are still trying to reproduce this issue, But it has not been reproduced yet. I upload a new test fw to ftp server. Path: /release_by_fxn/smart3_test/network_error/k000b-534r18c_SD-20220815-BFX-AT100/ Can you help update fw and provide dmesg and logcat? Thank you Dean Chiang |
|
|
HI Dean / Bcan Please check the attached log. The final state of the log is that the network is not available even though the network cable is plugged in last cable plug-in time is [08-16 12:10:48] After the above issue has been observed, The network was restored after ifconfig eth0 down / up command at serial terminal. The FW used is as follows. /release_by_fxn/smart3_test/network_error/k000b-534r18c_SD-20220815-BFX-AT100/ [ro.vendor.vasott.version]: [k000b-534r18c_SD-20220815] Thank you YK.Jung |
|
|
Hi Younkwang, I upload a new test FW to fix this issue. Please help to verify the test FW. Path: /release_by_fxn/smart3_test/Mantis1519_network_error/k000b-534r18c_sleepmode_SD-20220822-BFX-AT100 Thank you Dean Chiang |
|
|
Hi Dean I sent it to the QA team I'll let you know after the test. Thank you YK.Jung |
|
|
Hi Mr. Dean Chiang, I have question. Did you reproduce this issue in your office ? What is the changes for new Test ? Did you test it in your side ? If yes, then please share your test result. Best regards, SuhYoung YOON |
|
|
HI Dean The issue occurred again in the FW you sent me. [ro.vendor.vasott.version]: [k000b-534r18c_sleepmode_SD-20220822] The time when the issue occurred is 08-23 08:46:17.177 The network connection is not working after this time. [kernel.log] 08-23 08:46:17.177 0 0 W : [ 532.639298@1] addr = 0, regnum = 1 08-23 08:46:17.177 0 0 I : [ 532.639349@1] meson6-dwmac ff3f0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx ==> connect LAN cable to STB [logcat.log] 08-23 08:46:17.195 I 3514 3514 netd : setIPv6AddrGenMode("eth0", 0) <0.12ms> 08-23 08:46:17.197 I 3514 3514 netd : interfaceSetEnableIPv6("eth0", "true") <0.72ms> 08-23 08:46:17.197 E 4692 6088 native : E0000 00:00:1661211977.197893 6088 ip_address_util.cc:51] Failed to connect UDP socket 08-23 08:46:17.198 E 4692 6088 native : E0000 00:00:1661211977.198092 6088 ip_address_util.cc:20] Failed to get netmask 08-23 08:46:17.199 E 4692 6088 native : E0000 00:00:1661211977.199416 6088 ip_address_util.cc:51] Failed to connect UDP socket 08-23 08:46:17.199 I 3514 3514 netd : setProcSysNet(4, 2, "eth0", "retrans_time_ms", "750") <0.13ms> 08-23 08:46:17.199 E 4692 6088 native : E0000 00:00:1661211977.199581 6088 ip_address_util.cc:20] Failed to get netmask 08-23 08:46:17.202 I 3514 3514 netd : setProcSysNet(4, 2, "eth0", "ucast_solicit", "5") <0.14ms> 08-23 08:46:17.203 I 3514 3514 netd : setProcSysNet(6, 2, "eth0", "retrans_time_ms", "750") <0.21ms> Please check it Thank you YK.Jung |
|
|
Hi Mr.Yoon, We can reproduce this issue, but it is not very easy. And we found another related situation. According to the steps below, it's easy to find that eth0 doesn't show up in ifconfig command. 1. boot up Smart3 without inserting ethernet cable 2. check ethernet interface (ifconfig) 3. soft reboot 4. check ethernet interface (ifconfig) 5. repeat step 3-4 The new test image includes a fix about this situation. And we thought this might improve the original issue. |
|
|
HI Dean Please update the progress. Thank you YK.Jung |
|
|
Hi Younkwang, Could you provide the brand/model of the router that you use to reproduce the issue? |
|
|
HI Bcan - My environment: SK broadband device ( GIGA WIFI WAVE2 ) - QA Team Environment: iptime device ( H6008-IGMP) This issue is observed in both of the above environments. Thank you YK.Jung |
|
|
HI Dean/Bcan Please update the progress. Thank you YK.Jung |
|
|
Hi Younkwang, We sent a smart3 to Motorcomm. Their RD is checking this issue. And we are also checking this with Amlogic. |
|
|
Hi Younkwang, We have a new test image uploaded to ALT ftp. path: /release_by_fxn/smart3_test/Mantis1519_network_error/k000b-534r18d_phy12_SD-20220905-BFX-AT100 Please help to check if the error happens or not. If the error happened again, please collect more information for us to analyze. 1. Place the attached file "phyreg" under /data of smart3. 2. commands - cp phyreg /data - chmod +x phyreg - ./phyreg eth0 0x1e 0x27; ./phyreg eth0 0x1f (execute this command in one line) 3. provide the output of the above command to us phyreg (11,076 bytes) |
|
|
Hi Bcan FW is console:/data # getprop | grep ro.vendor.vasott.version [ro.vendor.vasott.version]: [k000b-534r18d_phy12_SD-20220905] After netwrok Issue Occurred console:/data # ./phyreg eth0 0x1e 0x27; ./phyreg eth0 0x1f write phy addr: 0x0 reg: 0x1e value : 0x27 read phy addr: 0x0 reg: 0x1f value : 0x2010 Please let me know if you need anything. Thank you YK.Jung |
|
|
Hi Younkwang, After discussing with the vendor, we need to do HW rework that move the resistor on R810 to R811 to get improved result as attached picture. Bcan will provide the SW related info for further verification. Thanks, Jay. Eagle_2nd PHY_Rework.jpg (135,282 bytes) |
|
|
Hi Younkwang, Please help to apply the above HW rework and use FW (k000b-534r19_SD-20220716-BFX-AT100) to test again. You can find the FW in your FTP site. (path: /release_by_fxn/smart3/0716_534r19_at100) |
|
|
Hi Mr. Sean Chiang, It is HW changes. So could you add your comment about HW change ? @Mr. Lonnie KIM and Mr. SC Joung, Could you check it and discuss with FII HW engineer if you have any concern ? BR S YOON |
|
|
Hi, Jay Lin and Sean Chiang I have question about your HW change. Why RTL8211F don't have this issue in spite of pull-up? I think Motorcomm need to verify about ALDPS mode of RTL8211F. Could you discuss with Motorcomm? Best regards Lonnie Kim |
|
|
Hi Jay Lin / Bcan Our HW engineer did the same test after modifying it as you requested. As a result of the test, the issue continued to be observed Please check the attached log. The last state of the log is network unavailable even though the LAN cable is connected. Thank you YK.Jung |
|
|
Hi Younkwang, How many rounds (remove cable, wait 5 min, insert cable) did you test to reproduce this issue? |
|
|
Hi Mr. Bcan We could reproduce this issue with following steps : 1. Remove Ethernet cable from STB for 10 min. 2. Connect ethernet cable to STB for 1 min. 3. Repeat step 1 to 2 for 5 times. Thank you joung |
|
|
Hi YK, Joung, May I know if this issue happened on SWAN 2nd source boards with Motorcomm phy ? BTW, may I know how many rounds you can reproduce this issue between original and reworked boards? Thanks, Jacky |
|
|
Hi Jacky This issue did not occur in SWAN 2nd board with Motorcomm-phy. (QA tested it in the same network environment) This issue is only occurring on Smart3 2nd board. When I and QA Team test it with Smart3 second board, it happens at least once within 2 hour. (it is random) (Both My Network Environment and QA network Environment ) and the HW team didn't do many tests with the reworked board. If this issue did not occur, HW team would have continued to test, but the test was stopped due to the same issue at the reworked board. Thank you YK.Jung |
|
|
Hi Younkwang, After discussing with the vendor, we need ALT to do HW rework to get improved result as attached file(rewrok1~3). Thanks, Cooper |
|
|
Hi Cooper Kung, Test results reproduced the problem below the rework(1-3) sample. reproduce this issue with following steps : 1. Remove Ethernet cable from STB for 15~20 seconds 2. Connect ethernet cable to STB for 15~20 seconds. 3. Repeat step 1 to 2 for 24 times. Additionally,Request the following information to check network issues. 1. Motorcomm YT8531c desgin guide. 2. YT8531c reset timing spec. 3. YT8531 electrical spec. 4. LG1P109RN LF(LAN Magnetics) desgin guide. Thanks jung |
|
|
Hi Sun Choul Joung FYI Thanks Cooper |
|
|
Hi Mr. Sean Chiang and Mr. Cooper Kung, I uploaded Video clip for reproducing issue. The test sequence is as follows : reproduce this issue with following steps : 1. Remove Ethernet cable from STB for 15~20 seconds 2. Connect ethernet cable to STB for 15~20 seconds. 3. Repeat step 1 to 2 for 24 times. If you have any question, please let me know. BR, S Y Yoon 2ndSrcReprodSeq.mp4 (5,908,807 bytes) |
|
|
Hi, Joung We rework another Eagle PCBA and the test result are as below. 1. Before rework (YT8531C + current Eagle's transformer circuit design): test 100 times, fail rate 2% (fail occurs at 82nd and 100th time) 2. After rework (YT8531C + SWAN's RJ45 connector): test 130 times, fail rate 2.3% (fail occurs at 110th, 112th, 118th time) software version: 15.534.19 Thanks ! Tom |
|
|
Hi Mr. Tom Lee, So your test result is same as us. There is no change with RJ45 connector. As we discuss weekly meeting, please check it AML EVB that has motorcomm PHY. Best Regards, SuhYoung YOON |
|
|
Hi Dean Smart3 ethernet phy change have been cancelled. So I'll close this ticket. Thank you YK.Jung |
- yk.jung ( (ALTech) Younkwang Jung ) developer
